home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
gt_power
/
noans203.zip
/
NOANSWER.DOC
next >
Wrap
Text File
|
1991-02-09
|
10KB
|
214 lines
┌────────────────────────────────────────────────────────────────────────────┐
│ No─Answer? v2.03 Oliver Bell 013/000 │
└────────────────────────────────────────────────────────────────────────────┘
Well, it's time to take a look at another new posibility for a utility for
GT POWERcom, this one is for users of GT15.50 and above only and takes
advantage of the fact that an un─answered page is now logged in the GT.LOG.
It's nice and simple to use, all you have to do is to write three short
messages and then run the program in your GTLOGOFF.BAT file.
First thing you have to know about are the command line parameters ─ these
are used to overide the name of the file that No─Answer? will convert into
a message.
There are three differant messages that the program, one to the sysop informing
him/her of the un─answered page, one that would be sent to the user if he/her
paged within the time specified in the OFFICE= bit in SCHEDULE.BBS and one for
a user who paged outsie this time.
There are three default file names for these which are :─
SYSOPIN.LTR ─ Sent if page is un─answered during office hours
SYSOPOUT.LTR ─ Sent if user tried to page outside office hours
SYSOP.LTR ─ Sent to the sysop whenever!
there are corresponding command line parameters to these for example to use
a file called SYSMES.TXT for the messageto the sysop you'd use the command line
NOANSWER SYSOP:SYSMES.TXT
note: SYSOPOUT:????????.???
SYSOPIN:????????.??? both work to re─name the corresponding message.
all the file names are read from GTPATH only ─ sorry to put another file
in there but it seemed like a good idea at the time.
You can also prevent the program from sending any of the messages by typing
'NOLETTER' as the file name e.g. if you wanted to prevent the letter going to
the sysop you would use the command line 'NOANSWER SYSOP:NOLETTER'.
The only other command line option is the 'register' option that will
cause the program to netmail me at my 050/030 node, just to let me know that
you're using the program. With that facility I can work out who is using the
program and weather it's feasable to continue development of it.
────────────────────────────────────────────────────────────────────────────────
The Contents Of The Message
~~~~~~~~~~~~~~~~~~~~~~~~~~~
The message is made up on the whole of standard text BUT it is possible to
put one or two things in there to personalise the message a little.
%%FNAME ── will be exchanged for the user's first name when the message
is posted
%%LNAME ── will be exchanged for the user's last name
%%NAME ── will be exchanged for the user's full name
%%SFNAME ── will be exchanged for the sysop's first name when the message
is posted
%%SLNAME ── will be exchanged for the sysop's last name
%%SNAME ── will be exchanged for the sysop's full name
%%OOFFICE ── will be changed for the sysop's opening office time
%%COFFICE ── will be exchanged for the sysops closing office time.
e.g. Dear %%FNAME, when the message was posted would become
Dear Oliver, (or the first name of the current user)
the opening and closing office times would be used in the SYSOPOUT.LTR
e.g. a line that looked something like
I'm normally available for pageing between %%OOFFICE and %%COFFICE.
would become
I'm normally available for pageing between 7:30 and 23:30.
Please take a look at the sample message files contained within this archive.
If you have any further problems or ideas for this program then please don't
hesitate to contact me either via netmail (013/000) or call the board direct
on +44 (0)254 682862. (The Wind) Dual Standard HST.
┌─────────────┬──────────────────┬─────────────────────────┬─────────────────┐
│ Oliver Bell │ The Wind │ +44 (254) 682862 │ GT Network │
└─────────────┴──────────────────┴─────────────────────────┴─────────────────┘
────────────────────────────────────────────────────────────────────────────────
Version 1.01 ── Added Facility to use sysop's name as a variable. Thanks go
(09─02─90) to Mike Robinson of 050/033 (On─Line Support)
Also added the 'NOLETTER' bit to prevent the program sending
a message under certain conditions.
────────────────────────────────────────────────────────────────────────────────
Version 1.02 ── Added Checking for ;TWIT and NO CARRIER entries in
(16─02─90) GT.LOG check, once again many thanks to Mike Robinson.
mmm ─ well another one from the same guy again. It is now
possible to post the messages in areas other than the
standard sysop message base. Just put the message that you
want to send in with the control files for that area, make
sure that No─Answer knows what the file is called (this is
not nessacary if your using one of the standard file names),
and hey presto ─ the message will appear in that area.
This facility works in a similar way to the WELCOME.BBS/CBS
in GT ─ see the GT HOST docs or netmail me directly if
you need more help.
The other change in this version will help you when
testing other GT utilities that rely on the entry
in the GT.LOG 'PAGE NOT ANSWERED'. Adding the word
'LOCAL' to the command line will prevent the program
from sending any messages at all if the last user was
on in local test mode.
────────────────────────────────────────────────────────────────────────────────
Version 1.03 ── Minor bug fix.
(21/02/90)
────────────────────────────────────────────────────────────────────────────────
Version 1.04 ── Corrected problem with NOLETTER option, my thanks go to
(26/02/90) Mike Heggan of UFF DA Express II (56/1) for reporting
the problem to me!
────────────────────────────────────────────────────────────────────────────────
Version 1.05 ── Minor bug fix.
────────────────────────────────────────────────────────────────────────────────
Version 1.06 ── Noanswer will now give you a reason for not sending
messages to a user on the screen.
I have also added support for the 'REASON:' bit
recently introduced into GT 15.50.
Just put '%%REASON' as the only word on one of the
lines in the message to the sysop and you'll suddenly
find the message a whole lot more helpful! NOTE: This
option works only in the letter to the sysop.
────────────────────────────────────────────────────────────────────────────────
Version 1.07 ── Fixed problem with page reason not being displayed when
it was less than two lines in length.
────────────────────────────────────────────────────────────────────────────────
Version 1.08 ── Corrected problem that arose when running SHARE,
NOANSWER is now totally SHARE comptable. Now that
GT15.50 has been released this is the final relaese
version of NOANSWER.
────────────────────────────────────────────────────────────────────────────────
Version 1.09 ── Well, one step forwards and one step backwards, I've
added support for the xBS path in GT15.50 (long
overdue) BUT at the same time the SHARE compatibility
has been temporally removed, this will return soon.
────────────────────────────────────────────────────────────────────────────────
Version 1.10 ── Re─Introduced the SHARE support, sorry for the
(01/08/90) inconveniance it caused to those running LAN based
systems. Many thanks to John Della─Torre for the gentle
push.
Also from OZ, the suggestion to be a little more
careful as to when I actually send a message from the
NoAnswer Program, Warren Leadbetter suggested that I
look for the ';CARRIER LOSS' which I should have been
doing all along, ah well! there should be less
duplicate messages mow anyway.
────────────────────────────────────────────────────────────────────────────────
Version 1.11 ── Added checking to the READLOG procedure, the error that
(19/08/90) used to appear when the LOG had less than 20 lines in
it should now dissappear.
Also added the facility for displaying the reason for
page in the message to the User as well as the sysop.
The program has now been LZEXE'd as well to save a
little disk space for us all, before LZEXE the program
is 30K in size and 14K afterwards, a 16K saving accross
all 570(ish!) nodes in the GT network, also on the
basis that everybody uses the program that should save
about 9Mb worth of disk space <grin>.
────────────────────────────────────────────────────────────────────────────────
Version 2.00 ── Minor Bug Fix. Also GT16 compatibility is now running
and functional although totally transparant. NOANSWER
is not a utility you will have to worry about when you
upgrade to the new GT it will just run under whatever
version you wish it to.
This version has also had a bit of a face lift and one
or two major changes internally.
────────────────────────────────────────────────────────────────────────────────
Version 2.01 ── Again, a Bug Fix, correcting a problem reported by Steve
Thompson at 302/006 with the NOLETTER function, NoAnswer
was still trying to delete it's work files even when it
haden't actually posted any messages.
────────────────────────────────────────────────────────────────────────────────
Version 2.02 ── Corrected a Bug reported by Phill Piddell connected with
2.03 NoAnswer looking for USER.CTL on a LAN based system.